Vehicular dual mode master/slave interface

ABSTRACT

A vehicular interface may include an electromechanical interface between a hand-held electronic device and subsystems on a vehicular bus or network. In selected embodiments the interface may operate in a “master mode” when a handheld device, such as a tablet computer or smart-phone, is not inserted therein. In this mode the interface may serve as a master controller and accesses and controls various subsystems on a vehicle (such as engine control subsystems, media controllers, navigation systems, sensors and transducers) as a master controller. In one embodiment, when a tablet device is inserted into the interface, the interface may automatically switch to “slave mode” in which it acts as an adapter or interface between the tablet device and the vehicular subsystems. In this mode of operation the user&#39;s exclusive interface is through the tablet computer and the tablet computer serves as the master controller for the system.

CROSS-REFERENCE TO RELATED CASES

The instant application is related to and claims priority to thefollowing U.S. patent applications, the entirety of each of which isherein incorporated by reference.

Serial No. Title Filing Date 61/617,277 Master/Slave Interface Device 29MAR. 2012 61/623,222 Interfacing Handheld Devices 12 APR. 201261/621,497 Keystone Synchronization System 07 APR. 2012 61/621,630Interfacing Handheld Devices 09 APR. 2012 61/621,495 PhoneBook andTabletBook 07 APR. 2012 61/603,330 On-Board System 26 FEB. 201261/597,045 On Board System 09 FEB. 2012

SUMMARY OF ILLUSTRATIVE EMBODIMENTS

A vehicular interface may include an electromechanical interface betweena handheld electronic device and subsystems on a vehicular bus ornetwork. In an illustrative embodiment, the interface may operate in a“master mode” when a handheld device, such as a tablet computer orsmart-phone, is not inserted therein. In this mode the interface mayserve as a master controller and accesses and controls varioussubsystems on a vehicle (such as engine control subsystems, mediacontrollers, navigation systems, sensors and transducers) as a mastercontroller. In one embodiment, when a tablet device is inserted into theinterface, the interface may automatically switch to “slave mode” inwhich it acts as an adapter or interface between the tablet device andthe vehicular subsystems. In this mode of operation the user's exclusiveinterface may be through the tablet computer while the tablet computerserves as the master controller for the system.

This approach in selected embodiments can provide one or more of thefollowing advantages. First, this system may provide enhancedfunctionality at reduced cost by relying on the computing power andfunctionality of a tablet computer that was previously acquired by theuser. The interface may be configured to have limited functionality inmaster mode and intended to operate primarily in slave mode.Accordingly, relatively inexpensive processors, memory and displayscreens can be used to implement the interface because it is expectedthat the interface would typically be operating in slave mode. Second,this system may substantially reduce the time needed for a user tobecome proficient with the system. This stems from the fact that theusers generally will already be familiar with their handheld device'soperating system, user interface and functionality. Third, this systemarchitecture may facilitate continuous updating and improvement byenabling software updates and new software modules to be pushed to theuser's tablet PC or smart phone. Fourth, this system architecture mayenable a user to port most or all of the system's functionality toanother vehicle that is appropriately equipped with a compliantinterface. Indeed, even when the other vehicle is not so equipped, thetablet device may still provide some or most functionality as astand-alone unit.

The details of one or more implementations are set forth in theaccompanying drawing and description below. Other features, objects, andadvantages will be apparent from the description and drawings, and fromthe claims.

BRIEF DESCRIPTION OF FIGURES

FIG. 1 is a block diagram of an illustrative MSID embodiment.

FIG. 2 is a state transition diagram for an illustrative MSIDembodiment.

FIG. 3 is an illustration of the basic functionality of an illustrativeMSID embodiment.

FIG. 4 is an illustration of the basic functionality of an illustrativeMSID embodiment from a user perspective.

FIG. 5 is a subsystem block diagram for an illustrative MSID embodiment.

FIG. 6 is another subsystem block diagram for an illustrative MSIDembodiment.

FIG. 7 is yet another subsystem block diagram for an illustrative MSIDembodiment.

FIG. 8 is an interface diagram for an illustrative MSID embodiment.

FIG. 9 is a process flow diagram for an illustrative MSID embodiment.

FIG. 10 is another process flow diagram for an illustrative MSIDembodiment.

FIG. 11 is a table of potential applications.

FIG. 12 is a schematic of a hardware-centric system architecture.

Like reference symbols in various drawing indicate like elements.

DETAILED DESCRIPTION OF ILLUSTRATIVE IMPLEMENTATIONS Overview ofSelected Embodiments

Many modern vehicles, such as automobiles or watercraft, have aplurality of onboard sensors and display devices capable of measuringand displaying various vehicular-related data. Examples of this includedepth sounders and GPS systems on watercraft. It is desirable to havethe capability to interface with all the on-board devices with arelatively inexpensive, and probably previously purchased externalcontrol and display device (ECD), which, for example, could be apersonal hand-held smart device, such as an iPhone® or iPad® mobiledevice (trademarks of Apple Inc.), or other handheld processor-baseddevice. In one preferred embodiment, the ECD is a tablet PC or smartphone device which electrically and/or mechanically couples to aprotective receptacle on a boat, for example, that provides on-demandlake maps, location information, tactical “fishing guide” advice andemergency services.

FIG. 1 is a block diagram of an illustrative MSID embodiment. Thesystem, in certain embodiments, utilizes a previously purchased tabletor smart phone and thus provides all of this functionality with anabsolute minimum of investment in new hardware and on a device runningan operating system with which the user is already familiar. Theprotective receptacle provides power and connects to accessory devicesvia auxiliary network communication systems such as cellular, GPS, Wi-Fiand satellite systems; auxiliary user interfaces such as keypads, touchscreens, speakers and headsets; emergency beacons; sensors that detectone or more of air temperature, water temperature, water depth,barometric pressure, change in barometric pressure, wind direction, windspeed; and protective means that render the on-board systemsubstantially weather proof and shock resistant.

However, if an ECD is not present, it may be appropriate in certainembodiments to have a stand-alone device which serves the same basicpurpose as the ECD, displaying selected External Onboard Device (EOD)data, which data may originate from a temperature sensor, GPS, or depthsounder, for example. Without an ECD, this data control and display canbe independently controlled by built-in control and display functions,or any of the external display devices that are present.

Some remote displays (e.g., in marine applications) allow the user toselect and display available vehicular-related data. In some cases, suchexternal display devices (EDD) are all-in-one, stand aloneDisplay/Sonar/GPS/Chart Plotter devices that are quite complex andexpensive. In various embodiments, an exemplary Master/Slave InterfaceDevice (MSID) may advantageously enable the same display functionalitywith less expensive EDDs. The MSID in certain embodiments can enablethis with its data routing and device polling capabilities. In anillustrative example, the MSID can read the commands from each and allof the EDDs, interpret these, and send the requested data to each of theremote displays. In this way, complex and expensive remote displays arenot needed in such embodiments, yet independent data selection anddisplay is maintained.

In selected embodiments, the MSID is a device which can serve as masteror slave to a plurality of external onboard vehicular devices such asdepth sounders, GPS, thermometers, etc. These devices optionally includethe capability to provide wireless communications to convey controland/or data messages via, for example, Bluetooth or Wi-Fi. In eithercase, the MSID will have the capability to network with the externalonboard devices (EODs) for the purpose of consolidating the considerableamount of data associated with these devices to a user friendly andconvenient control and display.

Various embodiments of the MSID can serve as a master control anddisplay, a state in which the MSID selects which EOD data to display,and displays these data on its built-in display. In addition, the MSIDmay allow an ECD, such as a PDA, iPad, or PC, to act as a master to theaforementioned sensor network. In this state, the MSID acts as a slaveto the ECD, merely passing or routing EOD data to the ECD. The MSID mayhave the capability to automatically sense the presence of an ECD, andallow it to be the master control and display device. This transitionmay be purely automatic, with the option of a manual input verifying oroverriding this decision by the MSID.

The MSID, in an illustrative embodiment, is a dual mode master/slavedevice that includes an enclosure to securely retain an ECD, and perhapsa plug which electrically couples to the ECD. In some embodiments, theECD may operate remotely via a wireless connection to the MSID. The MSIDunit may include a multi-level power converter to provide, from anexternal power source such as a vehicle battery for example, appropriatesupply voltages to the ECD and, optionally, the EODs. The MSID alsoincludes analog to digital converters (ADCs) and digital to analogconverters (DACs) as necessary to enable the MSID to communicate withanalog EODs. The MSID further includes wireless communication means suchas Zigbee, Bluetooth and Wi-Fi in order to wirelessly couple withexternal sensors and the ECD, if it is so equipped.

The MSID housing in selected embodiments includes a recess with multiplecontoured regions or adjustable/interchangeable mounts to mateably andreleasably receive an ECD such as a smart phone or tablet device. Thehousing optionally includes, for example, water resistant sealing system(e.g., IP rated) to resist the ingress of water, or shock absorbing anddampening features on the housing to insulate the ECD from water,vibration, or weather. The MSID also includes a transceiver to receiveuser commands from a wireless remote control and transmit the commandsto the ECD. Such commands may include user inputs to control variousapplications running on the ECD such as music players, lake mappers,fish finders/sonar, navigation systems, and the like. The MSID housingmay also communicate with an emergency rescue beacon (ERB) (or perhaps abuilt-in ERB) which automatically generates distress signals inappropriate circumstances based on a command provided from the ECD orMSID.

The system may further include a redundant communication subsystem thattakes the form of a Wi-Fi hotspot, a cellular modem with an alternativewireless carrier, a GPS system, and/or a satellite internet connection.This redundant communication system can provide connectivity when acommunication means built into the ECD is unable to connect to thenetwork.

In either mode (MSID Master or MSID Slave), the MSID optionally alsoallow the EDDs to remotely request and display all, or a subset ofavailable data. The MSID will read the requests from each EDD that ispresent, and send to that EDD, the particular data it requested. In thisway, the EDDs can independently display user requested data. This is acapability that may be particularly useful in a watercraft application.

In order for the MSID to accomplish the intended operations, thefollowing set of basic MSID system capabilities pertain. Many of thesecan be optional depending upon the specific embodiment.

In the absence of an ECD, the MSID system may display available EOD dataas selected by the MSID GUI. The MSID may also output commands, asappropriate, to selected EODs. These commands will be selected by theuser via the GUI, and will include status requests, data requests, andother EOD specific commands. This will allow the MSID to act as a mastercontrol and display device in a standalone capacity (i.e., in theabsence of an ECD). In order to accomplish this, the MSID system willaccept and perhaps store inputs from the various EOD, which may have aBluetooth, Wi-Fi (or any other wireless link as needed), or hardwiredcapability as appropriate. A hardwired capability may be considered asoptional on certain models of the MSID.

When an ECD is present, the MSID system may output to the ECD those EODdata selected by the ECD. In this way, the MSID acts as a slave, being asimple data router or pass-through function, enabling the ECD to operateas the master control device for the MSID system and the peripheralEODs. If the ECD is not connected directly to the MSID, the MSID datamay be output wirelessly to the ECD via Bluetooth, Wi-Fi, or otherpertinent wireless links. Otherwise, the MSDI may output data over thehardwire connection. In order to satisfy this requirement, the MSID willneed to accept and perhaps store data from the EODs and the ECD via anoptical (e.g., infrared, fiber optic) or wireless link that may benecessary. The MSID will also exchange data with the ECD if it isconnected to its docking cradle.

The MSID may supply a standard iPhone/iPad interface cable, includingpower supply signals, to enable such devices to be cradled into theMSID. This will allow these ECD devices to be mechanically plugged intothe MSID, communicate with it, and supply power to it. The MSID may alsoprovide a mechanical receptacle which is compatible with the morepopular smart devices that may act as an ECD. In this way, the ECD canbe literally plugged into the MSID, which can provide mechanicalstability and some degree of environmental protection to the ECD.

The MSID may also supply power to one or more of the EODs, EDDs, as wellas ECD as necessary. This could be optional depending upon theimplementation.

The MSID may have the option to display any data/information while inthe MSID Slave state. This data could simply repeat the data beingdisplayed by the ECD, or include health or status data, for example.

If the MSID has its own built-in display capability, the brightness ofthis may only need to be the same or brighter than the iPad, forexample. An optional user input control (e.g., dial, key, soft key ontouch screen) to control the brightness of the display either manuallyor via automatic brightness control could be provided.

The MSID may be provided with audible outputs as necessary, anddepending upon the implementation. Warnings, like an EOD is offline,possibly indicating it has malfunctioned, or its power source died, aresome of the options for an audible output. Other operational data couldalso be output in an audible manner. By way of example, and notlimitation, these data could include depth alarms, indicating that acertain preset depth is reached, or a shallow water warning. An optionto include different audible outputs for different types of warning mayalso be included. External speakers may be added for this capability, inaddition to accommodating music/video playback operations.

The MSID may also have the capability to report/display system healthstatus. This would be an option that could be included on certainembodiments of the system. A built-in emergency rescue beacon could alsobe an option depending upon the implementation (e.g., the specific modelof the MSID).

Environmental conditions under which the MSID must operate could varydepending upon the specific embodiment. The iPhone operatingenvironment, for example, is given below:

Operating temperature: 32° to 95° F. (0° to 35° C.)

Non-operating temperature: −4° to 113° F. (−20° to 45° C.)

Relative humidity: 5% to 95% noncondensing

Maximum operating altitude: 10,000 feet (3000 m)

The interfaces between the MSID and the EODs, EDDs, and ECDs, could beoptional and can range from a hardwire (e.g., USB cable, RS-485, CAN,Ethernet), to optical (infrared), to fiber-optic, and/or any otherwireless protocol (e.g., Bluetooth, Wi-Fi, Zigbee). In the case of ahardwire interface, power could also be provided as an option.

The MSID may also provide the option for a backup internal powercapability, in case there is a malfunction or interruption in theprimary power supply. The amount of time the internal battery backupsystem lasts would be optional and dependent upon the specificembodiment(s). Various implementations may further include surgesuppression circuit elements, for example, to attenuate voltagefluctuations on a vehicular battery or alternator output buses.

The MSID may also act as a data router, sending specifically requesteddisplay data to the EDDs. Each of the EDDs will request specific datafrom the MSID. The MSID in turn will read the requests from each EDD,and then send those specific data to that EDD. In this way, any numberof EDDs may be present, and each will be able to independently requestand display specific data available from the MSID.

System Architecture

FIG. 2 is a state transition diagram for an illustrative MSIDembodiment.

The MSID will operate in any of several states as shown in FIG. 2. Thisalso shows the transition between the states of the MSID along with thetransition-enabling event.

The states shown in FIG. 2 are described below:

Power Down (OFF)—The state in which the MSID has no power applied, andno operations are being executed. In this mode, the EODs may or may notbe operating autonomously. The only way to transition out of this modeis to power up the system, which can be done by either by connectingpower, and/or turning on a power switch. The power down (OFF) state canbe transitioned to from any other state by disconnecting power, and/orturning off a power switch.

Power Up (ON)—This is a transitional state in which the MSID has beenpowered up from the Power Down (OFF) state. This can be accomplished byconnecting power and/or turning on a power switch. Since this state istransitional, the system will not stay in this state long, as it willtransition either to the MSID Master, or MSID Slave states. It is alsopossible to transition from this state to the power off state shouldpower be disconnected before the other transitions occur. Otherfunctions which may be performed while in this state include polling ofthe EODs and local Wi-Fi networks that are within communication range.This would be done to determine what devices are available, and whatdata might be displayed by the MSID, especially if it ended up in theMSID Master state. This polling could also be used to determine if anECD is present. In addition, system performance monitoring could beexecuted to determine the health of the system and its variouscomponents.

MSID Master—In this state, the MSID will act as the master. As a mastercontroller, the MSID will have control over the EODs, and control overwhich EOD data is displayed by the MSID. The MSID will transition intothis state in two ways: Upon power up, and no ECD is detected, or whilein the MSID Slave mode the ECD is not detected. This would occur forexample if the ECD becomes disconnected or runs out of power. In thisstate, the MSID will maintain control over which EOD data is selectedfor display onto the MSID built-in display function. A GUI will serve asthe control interface between the MSID and user. This can beaccomplished via a FOG display (touch screen), or mechanical switches,or a combination of both.

MSID Slave—In this state, the MSID will act as the slave, serving as amere data router or data pass-through to and from the EODs to the ECD ascommanded by the ECD. The MSID will transition into this state in twoways: upon power up and an ECD is detected; or, when in the MSID Masterstate, an ECD is detected. This allows the ECD to act as the mastercontrol and display device for the system. There is an option here toalso allow the MSID display to display the same EOD data as the ECD,and/or any number of other data (i.e. status, system health information,etc.).

Note that in either of the MSID Master or MSID Slave state, the EDDs, ifpresent, will be able to independently request and display availabledata from the MSID.

The operational concept of the MSID is designed to be very simple from auser's standpoint. The MSID provides an inexpensive human-machineinterface (HMI) to the plurality of EODs and/or EDDs that might bepresent on a vehicle such as a watercraft or automobile. Inexpensive inthe sense that not only the MSID itself will be cost effective, but theECD will already be affordable, and probably already purchased by theuser. The MSID will allow the user to use his/her ECD as the mastercontrol and display device, which will be complete with its own wirelessconnections, memory, processors, and user-oriented applications.

FIG. 3 is an illustration of the basic functionality of an illustrativeMSID embodiment. FIG. 3 illustrates the operational concept of the MSIDsystem. The MSID will operate from the onboard battery power supply. AnOn/Off switch can be provided to conveniently power up or power down theMSID. An optional built-in battery or the ability to use the battery ofthe ECD may also be provided as options in the event the vehicular powersource fails.

The MSID will interface and accept data from or transmit data to, theplurality of EODs and/or EDDs that are present and operational. The datalinks between the EODs, EDDs, and the MSID can be either Bluetooth,Wi-Fi, and/or possibly hardwire (such as an RS232 connection).

In various embodiments, the operational concept simplifies the userexperience in that the user merely boards the vehicle with or without anECD.

FIG. 4 is an illustration of the basic functionality of an illustrativeMSID embodiment from a user perspective. As shown in FIG. 4, once theuser boards the vehicle and an ECD is not brought on board, the MSIDwill not detect it, and will continue operating in whatever state it isin. The user simply uses the MSID directly to control and display EODdata (e.g., the MSID is the master control and display device).

If the user does have an ECD, the MSID will detect it (assuming it ispowered on), and may provide the user the option to make it the master.The user acknowledges this, and proceeds to use their ECD as the controland display for the ECD data (e.g., the MSID is the slave). If the userdecides not to use the ECD as the master, then the MSID will continue toact as master. This can be made automatic if desired, in the sense thatif an appropriate ECD is detected, the MSID automatically transitionsinto the slave state, giving master control over to the ECD. In eithercase, the user interaction is keep to a minimum.

The MSID may also advantageously enable relatively inexpensive EDDs tobe used for data display, rather than the more expensive all-in-one,stand alone Display/Sonar/GPS/Chart Plotter devices that are alreadyavailable and commonly used. The MSID does this by reading the requestsfrom each EDD present, and then sending the requested data to the EDDthat requested the data. The MSID will have this capability in eitherthe Master or Slave state. This is shown in FIG. 4.

The generic embodiment of the MSID system is decomposed into thefollowing subsystems:

1. Platform Subsystem (PFSS)

2. Transceiver Subsystem (TRSS)

3. Control and Display Subsystem (CDSS)

4. Digital Processing Subsystem (DPSS)

5. Clock Distribution Subsystem (CLSS)

6. Power Distribution Subsystem (PDSS)

A block diagram of these subsystems is shown in FIG. 5, followed by adescription of each. FIG. 5 is a subsystem block diagram for anillustrative MSID embodiment.

The Platform Subsystem (PFSS) is the primary mechanical interfacebetween the EODs, EDDs, and the ECD. It therefore contains any hardwiredinterfaces such as an RS232 interface with the EODs, EDDs, or ECD ifnecessary. This may be necessary if the option to provide power to theexternal devices is invoked. The PFSS provides the structure whichhouses all of the other subsystems, including a docking cradle for theECD. It may also contain a display of its own (part of the CDSS) to actas a master control and display when in the MSID Master state.

The Transceiver Subsystem (TRSS) provides all the communication betweenthe MSID and the EODs, EDDs, and any ECD that may be present. As such,it may include wired or wireless interfaces (e.g., for Bluetooth, Wi-Fi,and/or any hardwired interfaces) that may be necessary. It will alsoprovide the ADCs necessary to convert the incoming analog signals todigital for processing by the DPSS. It will subsequently also containany DACs necessary to convert and digital signals to analog fortransmission. Most of these conversions however will take place withinthe Bluetooth and/or Wi-Fi transceivers which will probably be containedwithin the TRSS.

In an illustrative example, Wi-Fi may be primarily used for connectingwirelessly to the internet, and Bluetooth may be primarily a shorterrange wireless interface to remote, but nearby devices, it isanticipated that, in some implementations, Bluetooth will primarily beused for these EODs and/or properly equipped EDDs, as well asinterfacing to the ECD, whereas Wi-Fi may be used for any wide areanetwork (e.g., internet) connections with the MSID.

The TRSS may send data to, and receive data from the DPSS. Properlyformatted EOD and/or EDD data will be transmitted to the DPSS, possiblyalong with EOD status. In return, the TRSS will receive commands fromthe DPSS to be transmitted to the EOD. Such signals may include a beaconcommand for example.

The TRSS may also receive a clock from the CDSS if necessary. Since mostwireless communication protocols are asynchronous, it is not anticipatedthat this interface will be necessary, but it included for completeness.

The Control and Display Subsystem (CDSS) may be the primary interfacebetween the MSID and the user when in the MSID Master state. In order tokeep costs down, the capability of this standalone mode may not be assophisticated as a modern ECD such as an iPad, but it will contain thebasic capability to control and display the EOD and EDD data. Oneembodiment could be a touch screen, similar to those found on many ECDsor EDDs. The control could be via finger on glass (FOG) commands on thisdisplay.

The CDSS will receive EOD/EDD data from the DPSS. This could already beformatted for display, or if not, the CDSS would perform any formattingthat may be required. This interface may be implemented by hardwiring tothe DPSS.

FIG. 6 is another subsystem block diagram for an illustrative MSIDembodiment. In the example shown in FIG. 6, EOD/EDD data transfers datadirectly from the TRSS via wireless link, such as a Bluetooth or Wi-Fi.In the latter case, a Bluetooth or Wi-Fi capability will be a necessarycomponent in the CDSS.

FIG. 7 is yet another subsystem block diagram for an illustrative MSIDembodiment. In this example, the DPSS could be an already availabledevice such as an iPad or iPhone, depicted in the figure as a SmartDevice-Based Subsystem (SDSS). These devices already have Wi-Fi,Bluetooth, hardwire communication capability embedded in them, inaddition to digital processors and user-oriented applications. Thiscould act as the CDSS, CLSS and DPSS. This may be accomplished, forexample, by communicating with the TRSS directly via a wireless link.FIG. 7 shows this optional implementation.

The Digital Processing Subsystem (DPSS) provides the processingnecessary for the detection and decision logic that will determine ifthe MSID transitions into the Master or Slave state upon power up. Thesedecisions are illustrated in the processing flow diagram of FIG. 9.

In order to make these decisions, the DPSS interfaces with both the TRSSand CDSS. In the slave state, the DPSS serves mainly as a data router ordata pass-through function, transferring data to and from the TRSS ascommanded by the ECD and/or EDDs.

When in the MSID master state, the DPSS receives commands from the CDSSand passes them to the TRSS. The EODs will receive these commands, andsend back the requested data to the TRSS. The DPSS will pass thereceived data from the TRSS to the CDSS for subsequent display.

In either state, the MSID will also accept display data requests fromeach EDD present, and route the requested data, if available, to theappropriate EDD.

In an exemplary embodiment, one or more dedicated and/or general purposecomputer chips may be used to implement the DPSS. As such, it may needan external clock. If this is necessary, the Clock DistributionSubsystem (CLSS) generates whatever clocks may be needed by the DPSS, orany other subsystem, and distributes them as necessary. Although somepoint-to-point communications, especially wireless, are asynchronous andmay not need externally generated clocks at all, the CLSS may beincluded for various implementations.

In various embodiments, the Power Distribution Subsystem (PDSS) may useas its primary source of power an external source, such as a vehicular12 Volt battery, for example. It may then provide the necessary powerconversion, most likely DC to DC in nature, to the various othersubsystem components, as well as possibly the EODs, EDDs, and/or ECDs.Typical devices in applications such as this could require voltages of 5Volt for devices like the iPhone, iPad, and iPod for example. Othervoltages may be generated as required by the specific embodiments.

Interfaces

Interfaces to the MSID are shown in FIG. 8, and include wireless links,like Bluetooth and Wi-Fi, as well as hardwire links (as necessary). Thehardwired interfaces may be optional, and not provided on some models ofthe MSID. In all probability, the EODs and EDDs will be in closeproximity to the MSID. Since Bluetooth wireless communications areinherently short range, it is this wireless link that will primarily beused between the MSID and EODs as well as appropriately configured EDDs.Bluetooth will also be one of the means to communicate with the ECD aswell. This is shown in the figure. The ECD may also contain a Wi-Fitransceiver, so this type of link could also be used for MSID-ECDcommunications, as well as a hardwire link. To link with a Wi-Fi hotspot for internet connectivity, Wi-Fi may be utilized exclusively. Acommon protocol for wireless links is the NMEA 0183 Standard. The NMEA0183 Standard defines an electrical interface and data protocol forcommunications between marine instrumentation, so this could be theprimary protocol used for the MSID. Other protocols exist, and will beused depending upon the specific implementation of the MSID.

FIG. 9 is a process flow diagram for an illustrative MSID embodiment.FIG. 9 depicts the basic processing flow diagram as the MSID systemtransitions from the Power Down (OFF) state to either the MSID Master orMSID Slave state, via the transitional Power Up (ON) state. It alsodemonstrates the transition from any active state to the Power Downstate, mainly by removing power. The DPSS is primarily responsible forthis particular decision process.

As with the state transition diagram (FIG. 2), this process embodies oneof the essential innovative aspects of the MSID. A more detailed processis shown in FIG. 10, which simply shows more of the operations thatwould be involved when the MSID is in its various states.

FIG. 10 is another process flow diagram for an illustrative MSIDembodiment. For example, in the MSID Master state, the MSID will pollthe available EODs, and set itself up as the control over them. It willalso set itself up to display EOD and EDD data as selected by the MSIDGUI, or as selected by the individual EDDs that are present.

In the MSID Slave state, the MSID may also poll the available EODs, butin this case it may set itself up to receive ECD commands, and serve asa data router, transferring EOD data as selected by the ECD, to the ECDfor display. The MSID need not itself be the source of the commands, norwill it need to display the selected EOD data. An option is to let theMSID go ahead and also display the selected EOD data, as well as sendingthe data to the ECD. As with the MSID Master state, the MSID in theSlave state may continue to accept display data requested by each of theEDDs, and route those data to the appropriate EDDs.

Applications/Implementation Options

The MSID concept as described in this document represents anadvantageous approach to networking various vehicular sensors using aninexpensive handheld smart device (ECD) as the main processing anddisplay function. In the absence of an ECD, the MSID will act as themaster control and display unit. If remote EDDs are present, the MSIDwill enable each to act as an independent unit, requesting anddisplaying specific, user requested MSID data.

FIG. 11 is a table of potential applications. There are severalapplications of this concept which will use various combinations of EODsand EDDs, and these are summarized in the table in FIG. 11 along withpotential links between the MSID and the peripheral devices. By way ofexplanatory example and not of limitation, the table includes codedestimates of probability that a specific peripheral and associated linkcould be used for various applications. Also indicated are peripheralsthat could be built-in to the MSID as an option. The variouscombinations of the peripherals and applications provide a myriad ofimplementation or design options for the MSID. Almost any combination ofsuch could be considered a specific implementation, with each gearedtowards a specific application.

EODs other than those mentioned to this point could also be a part ofthe MSID system. For example, if the MSID were to be used in a dwellingsuch as a home, camp, or office building, a motion sensor may beincluded as an EOD for security monitoring.

The table by no means attempts to constrain the number and types ofEODs, or EDDs that could be employed with the MSID concept describedherein. Other devices not mentioned here could be used, and will add tothe design options and utility of the MSID.

As examples of other vehicular contexts to which these principles may beapplied, MSID-based systems may be deployed in trains, ferries andairplanes. Such systems may be designed to provide passengersinformation and entertainment through their tablet computers while alsocharging the tablet device. Advertising and promotional offers can ofcourse be transmitted through the MSID to each passenger's tabletdevice. An MSID interface may be disposed at each seating location.

The MSID represents an inexpensive approach to the control andintegration of a network of peripheral vehicular-related devices.Various embodiments may enable an external smart device (e.g., iPhone,iPad, PC, etc.) to act as a master control and display for the entiredevice network. In this way, the relatively inexpensive smart device canbe used as a powerful master controller. It will have contained withinit the memory, processing power, display capabilities, and user-orientedapplications which will provide considerable flexibility in what and howvarious device data and information is displayed and/or used. It willalso allow for inexpensive remote display devices to be used forindependent data requests and display. For maritime applications, thesedata could take the form of fishing maps, water depth contour maps,weather conditions, water temperature, and more. This will requirelittle investment on the part of the user, and will obviate the moreexpensive all-in-one, stand alone Display/Sonar/GPS/Chart Plotterdevices currently in use.

In the absence of an external smart device, the MSID can and will act asits own master controller, providing in selected embodiments only basiccontrol and display capability. The MSID will be able to transition toeither state automatically by detecting the presence or absence of theexternal smart device. This will allow a backup control and display modein case the user forgets to bring his/her handheld device, or if thehandheld device malfunctions.

The MSID concept can be used on any vehicle, and is not limited toautomobiles or watercraft. In fact, the MSID can also be used in adwelling such as one's home or perhaps a camp. The MSID can beimplemented in a multitude of ways, and will depend upon the specificapplications and devices used. Several implementation concepts wereincluded in this document, but all of these have in common thecapabilities mentioned above.

Master/Slave Mode Functionality

FIG. 12 is a schematic of a hardware-centric system architecture.

A hardware-centric implementation is illustrated in FIG. 12. It will beunderstood that the functions of the controllers and adapters mayoptionally be performed in software, either within the operating system,drivers or in the application layer. It will also be understood that thearchitecture of FIG. 12 can be arbitrarily expanded by inclusion of moreperipherals, controllers, adapters, converters, control units,processors, buses, encoders, decoders, etc. and that the functionalityof an arbitrary fraction of those additional components can likewise bedeployed in software executed by a general purpose microprocessor. Theitems in dashed boxes are optional in the depicted embodiment.

With reference to the example of FIG. 12, a master unit (e.g. handhelddevice) interfaces with a slave/interface unit (e.g., an MSID) which inturn interfaces with a slave peripheral device (e.g., vehicularsubsystem controllers, sensors, transducers). The slave/interface unitincludes various network protocol adapters which are configured tocommunicate unidirectionally or bidirectionally with the peripheraldevices. The slave control unit (processor) arbitrates the communicationbetween the network protocol adapters and the handheld device adapters.The master unit bus operates on a master device protocol andcommunicates according to the protocol with the adapters which areinterfaced with the slave/interface unit.

Accordingly, the master unit communicates unidirectionally orbidirectionally with the slave peripheral devices directly orpseudo-directly in the sense that the slave/interface control unit is inone embodiment merely arbitrating the transmission of data through theslave/interface unit. In other embodiments the slave control unit or anoperating system or application program running thereon serves as aperipheral with a ported connection to the operating system of themaster unit and thereby serves as a translator or intermediary betweenthe master unit and the slave peripheral devices. In preferredembodiments the functionality of the slave control unit is minimized inorder to permit the use of inexpensive processors and memory. In suchembodiments the slave control unit does not execute processor overheadintensive or memory-access-intensive tasks but rather arbitrates thecommunications with the master controller.

In certain embodiments the slave control unit retains control of certaininterface operations with the slave peripheral devices. Fault detection,polling, clocking (if required) and related operations may be performedin the background by the slave control unit. The master control unitremains, in some examples, the sole or primary user interface. Themaster unit may provide, from the user's perspective, the main controlpanel for all vehicular operations associated with the peripheraldevices.

To this end, the master device optionally includes an applicationprogram or array of application programs which utilize data receivedfrom the various slave peripheral devices. In one embodiment, a singleapplication program includes various modules accessible through a singleuser interface screen. Each module performs a different category offunctions. For instance, a mapping and navigation module interfaces withthe GPS or location service related peripheral devices, displays anavigation map and enables route guidance and direction services. Afishing guide program interfaces with GPS or location based peripherals,sensor peripherals (depth and water temperature) and remote servers(fishing guide advice server, weather conditions server). Entertainmentmodules interface with associated peripherals, such as speakers andaudio input sources.

Access with remote servers in preferred embodiments is controlled by themaster unit operating system. If the master unit is equipped withcommunication means that permit an internet or private networkconnection the master unit operating system arbitrates and controls theaccess of remote servers as required by the application programs.Alternatively, the slave control unit operating system may act as acommunications peripheral by controlling a subordinate communicationmeans included in the slave/interface unit.

In this way, the operating system and application program(s) on themaster unit in a preferred embodiment act to provide the primary userinterfaces and network connections relied upon to support theapplication level functionality. Access to remote servers to obtaindirections, lake maps, software updates and downloads, subscriptionbased services, telephony, email, messaging, streaming media and thelike is managed by the master unit operating system and applicationprograms.

Updates in such embodiments may be executed conveniently by polling anddownload operations managed by the master unit's operating system andapplication programs. Additional and new software may likewise bedownloaded at any time an appropriate network connection is establishedby the master unit. Subscription based services may likewise by utilized(and enrolled in) when the master unit is mated to the slave/interfaceunit and optionally when it is not.

According to this embodiment, if the user upgrades his or her hand-heldcomputing device the functionality of the MSID system will likewise beenhanced. The software and settings from the user's previous handhelddevice may be ported over to the new device and new functionality may beprovided by the new master unit operating system and/or new applicationsoftware downloaded to the master unit.

In various embodiments a master unit application also manages theupdating and installation of software on the slave/interface unit.Periodic updates and new operating system and application programversions may be downloaded by and to the master unit and then installedon the slave/interface device.

The slave/interface unit may include an arbitrary amount of thefunctionality of the master unit, including redundant applications topermit similar control operations when the master unit is absent. Itshould be understood that in many embodiments provides the substantialadvantage that the slave/interface unit hardware and software will berelatively rudimentary and cost-effective because the system will beprimarily intended operate in slave mode, mated to a user's handhelddevice. For instance, the slave/unit interface processor speed(including clock speed) may be substantially lower than that of thehandheld device. Likewise, the main rapid access memory of the interfaceunit may have a substantially slower access speed and read/write ratethan that of the handheld device. The slave/unit interface may beequipped with a relatively inexpensive hard disk drive and the handhelddevice may be equipped with comparatively expensive nonvolatile memoryas a main storage means.

The slave/interface unit and master unit may communicate according to aclient/server model, the master being the server. The master unit maylikewise communicate with remote servers according to a client/servermodel, the master unit being the client in that communication. Theoperating system on the MSID, as discussed above, is configured to entera slave mode upon the insertion of a handheld device into a dockingcradle or mating of a handheld device to the MSID. The MSID may alsohave various software applications which interface with one or morevehicular subsystems. These programs include depth charting software,GPS location software, lake mapping software, navigation software,trolling motor control software, messaging software, and emergencyrescue beacon control software.

Housings

Although various embodiments have been described with reference to thefigures, other embodiments are possible. For example, the functionalityof a stand-alone GPS (e.g., the EDD as depicted in FIG. 1) may beprovided directly by the MSID coupled to an appropriate antenna. In someexamples, the antenna may be provided by a mobile cellular device withpre-existing GPS functionality that may be communicated to the MSID. Insome implementations, an antenna and appropriate receiver systems (e.g.,without a dedicated screen, software, and graphical user interface) mayprovide the requisite RF capability to determine location using softwareexecuted on the MSID, for example. Such embodiments may achieve reducedcomplexity and may reduce overall system cost and flexibility whilereducing redundant subsystems and while providing the user with afamiliar user interface via the MSID, for example. Such centralizationof functionality in the MSID may, in some examples, promote flexibilityin system implementation, allowing the user more choice in selectingquality and types of subsystem components for the application.

In an illustrative example, an exemplary system may be implemented on aboat such as may be used for fishing. The system may be operably coupledto communicate data, commands, and/or status to a propulsion systemand/or a steering system. In some implementations, the propulsion andsteering may be electronically controlled, such as commerciallyavailable, for example, as the Minn Kota Terrova™ trolling motors soldby Thorne Bros. of Minnesota. As bow mounted motors, the MIDS mayoperate in slave or master modes to provide steering information to themotor based on position information, which may be generated directly bythe MSID via an antenna interface, or received from a stand-alone EODwith GPS capability in response to a request for location packettransmitted from the MSID.

In an example, the MSID may be programmed in real time to learn a trackof positions and times (or speeds) that can be stored in a memory in theMIDS or ECD as the track is being physically followed by the boat (e.g.,could be any other type of vehicle). Offline, tracks may also beprogrammed into the MIDS or ECD by users or downloaded or generated as asuggestion by a computer running specialized software, for example. Suchprogrammed tracks may be intended to guide the boat under the steeringand propulsion of the bow mounted motor, under the control of the MSIDand/or the ECD via the MSID. In an illustrative example, one or morecomputer generated (suggested) tracks may be designed to guide the boatto specific locations based upon depth chart information, and mayfurther control propulsion to optimize trolling depending thepredetermined depth information, and to optimize speeds whentransitioning between trolling regions (e.g., when moving to differentspots). The tracks may be automatically adapted based on the time of dayand temperature, in accordance with user's predetermined input criteria.

As an example, a suggested track at an unfamiliar lake may beauto-suggested by specialized software according to user's predeterminedcriteria and to depth information downloaded onto a tablet computer. Theuser carries the tablet computer with the auto-suggested trackinformation onto a fishing boat. Upon coming into Bluetooth range of theboat, the MSID establishes a link with the tablet computer acting as themaster device. The user inserts the tablet computer into a splashresistant protective housing that is sealed against ingress of water toprotect the tablet. The housing has an aperture to permit user access tothe touch screen. The user runs an app that, when executed, causes thetrolling motor to propel and steer the boat efficiently to initiate thepredetermined auto-suggested track. The tablet computer (ECD)communicates with various EODs and EDDs via the MSID. For example, thedepth profile and track and temperature information may be received fromappropriate transducers and GPS devices acting as EODs, and thendisplayed at various positions on small personal EDDs to each of theusers on the boat. The depth, track, and temperature display informationassembled by the ECD is distributed to the EDDs to keep each fisher onthe boat informed as to current conditions and potential opportunities.If the conditions change, such as temperature falling out of apredetermined, user-defined threshold range, the ECD may automaticallydetermine or suggest to advance the track to a second area or depthrange, according to predetermined user-input criteria.

In various embodiments, the user may pre-program a large number oftracks into the tablet computer while away from the boat and remote fromthe MSID. The user may also define criteria based on characteristics ofselected species of fish, and associate tracks with the criteria. Forexample, walleye may have different depth/temperature/calendar/time ofday criteria for auto-suggested tracks compared to criteria for smallmouth bass, for example.

In addition to providing communication via the MSID to propulsion andsteering, the system may, in various embodiments, be configured tocommunication data, control and/or status information, eitherunidirectionally or bidirectionally, with other vehicle-basedinstruments or systems. For example, the ECD may receive engineinformation (e.g., oil temperatures, fuel level, battery level, systemstatus), monitor miles per gallon of fuel (or equivalent units), hoursof operation, and maintenance schedules, for example.

As described in U.S. patent application Ser. No. 61/623,222, entitledInterfacing Handheld Devices, and 61/621,495, entitled PhoneBook andTabletBook, which are incorporated herein by reference, the handhelddevice may be installed in a variety of housings. In one embodiment, theslave/interface unit (MSID) includes a clamshell housing to retain andprotect the handheld master unit. The clamshell is optionallysubstantially waterproof or water resistant, at least when in the closedstate. The clamshell may also include rubber mounts, springs and/orviscous mounts or dampers which substantially absorb vehicularvibration. Tactile keypads may be omitted in maritime and automotiveembodiments. In such embodiments, the MSID may include essentially theupper half of the TabletBook clamshell device with an optional hingedcover (not shown) to provide water resistance.

MSID Memory Card Option

The MSID may optionally be equipped with a memory card slot andassociated adapter. In this embodiment SD cards containing proprietaryinformation such as lake maps can be inserted into the MSID and accessedby the MSID when it is in master mode and by the handheld device(through the MSID) when the MSID is in slave mode. In this mannerproprietary content such as lake maps, fish guide advice, contour maps,navigational data can be purchased in the form of a card as analternative to downloading that information through the handheld deviceor transceivers associated with the MSID.

Some implementations may realize another cost benefit in the ability toadd the MSID to existing peripherals and sensors (transducers, antennas,temp senders, speakers, displays, radar's . . . “off the shelfcomponents”) in an system already installed in a vessel or vehiclereducing the cost to retro fit a vehicle with a non-functional oroutdated stand alone/traditional system.

Some embodiments may achieve additional benefits in the ability toreceive streaming media (audio and/or video and/or data) on one display,for example, on half of a split screen style display while monitoringdepth, GPS, radar or any other of the system's sensors on the other halfof the same display. For example, streaming media may be displayed on acompletely different display at the same time. In marine applications,for example, some embodiments may provide the ability to download fromthe internet while routing data to local devices over a network.

A number of embodiments have been described. Nevertheless, it will beunderstood that various modifications are optionally made withoutdeparting from the spirit and scope of this disclosure. Accordingly,other embodiments are within the scope of the following claims.

What is claimed is:
 1. A maritime vehicular-to-handheld interface systemcomprising: a communications network or bus hardwired andcommunicatively coupled to a plurality of vehicular peripheral devices,the peripheral devices including at least a sonar; and a dual-modeinterface device coupled to the communication network or bus, theinterface including an interface processor, housing, user interface,display, power supply means, memory storage means, and means tocommunicatively couple with a handheld computing device, the memoryincluding instructions which when executed by the interface processorenable the dual-mode interface to switch between at least twooperational modes: i) a slave mode when a handheld computing device iscommunicatively coupled to the interface, wherein when in a slave modethe interface processor is a peripheral to the handheld computingdevice, the latter of which serves as a master controller which receivesinput from a user and which communicates with each of the vehicularperipheral devices, and ii) a master mode when a handheld computingdevice is communicatively coupled to the interface, wherein when in themaster mode the interface processor is a master controller whichreceives input from a user and which communicates with each of thevehicular peripheral devices; wherein the handheld device includes oneor more application programs which are configured to receive data fromand transmit data to one or more vehicular peripheral devices, whereinthe interface processor receives software updates retrieved by thehand-held computing device from a remote server, and wherein the housingincludes a receptacle to releasably retain and electrically couple thehandheld device to the interface processor and power supply means. 2.The system of claim 1, wherein the interface processor receives softwareupdates retrieved by the handheld computing device from a remote server.3. The system of claim 1, wherein when in the slave mode the handheldprocessor receives data retrieved by the interface device from avehicular peripheral device and transmits the data to a remote server.4. The system of claim 1, wherein the housing further includes means toprotect the handheld device from moisture and vibration.
 5. The systemof claim 1, wherein the peripheral devices further include a sonar andtemperature sensor.
 6. The system of claim 1, wherein the interface doesnot include a GPS, Wi-Fi or cellular communication device.
 7. The systemof claim 1, wherein the clock speed of the interface processor issubstantially slower than that of a central processing unit of thehandheld computing device.
 8. The system of claim 1, wherein theprocessing speed the interface processor is substantially slower thanthat of the handheld computing device.
 9. The system of claim 1, whereina memory access speed of the interface device is substantially slowerthan that of the handheld computing device.
 10. The system of claim 1,wherein the user interface is provided via the display.
 11. The systemof claim 1, wherein the handheld device is a tablet PC or a smart phone.12. A system comprising: a plurality of vehicular peripheral devices; ahandheld computing device; and a master/slave interface devicepermanently coupled to the plurality of vehicular peripheral devices andselectively coupled to the handheld computing device, the interfaceincluding an interface processor, bus, housing, user interface, powersupply, memory, and an adaptor to communicatively couple with a handheldcomputing device, the dual mode interface being configured to operate inat least the following modes: i) a slave mode when a handheld computingdevice is communicatively coupled to the interface, wherein when in aslave mode the interface processor is a peripheral to the handheldcomputing device, the latter of which serves as a master controllerwhich receives input from a user and which communicates with each of thevehicular peripheral devices, and ii) a master mode when a handheldcomputing device is communicatively coupled to the interface, whereinwhen in the master mode the interface processor is a master controllerwhich receives input from a user and which communicates with each of thevehicular peripheral devices; wherein when in the slave mode theinterface processor receives data retrieved by the handheld computingdevice from a remote server, and wherein when in the slave mode thehandheld processor receives data retrieved by the interface device froma vehicular peripheral device and transmits the data to a remote server.13. The system of claim 12, wherein the handheld device includes aplurality of application programs which are configured to receive datafrom and transmit data to one or more vehicular peripheral devices. 14.The system of claim 12, wherein the housing includes a receptacle toreleasably retain and electrically couple the handheld device to theinterface processor and power supply means.
 15. The system of claim 12,wherein the handheld device includes an application program which isconfigured to receive data from the vehicular peripheral devices. 16.The system of claim 12, wherein updates to an application running on theinterface processor are received from the handheld device.
 17. Thesystem of claim 12, wherein the handheld device is a tablet PC or asmart phone.
 18. The system of claim 12, wherein the housing furtherincludes means to protect the handheld device from moisture, temperatureor vibration.
 19. The system of claim 12, wherein the handheld computingdevice includes a plurality of applications each of which access one ormore vehicular peripheral devices.
 20. The system of claim 12, whereinthe processor interface is not configured to run said plurality ofprograms.
 21. The system of claim 12, wherein the interface device doesnot include a GPS, Wi-Fi or cellular communication device.